Playwright-ParaBank-Automation

Automation Strategy

Version 1.0.0 | Playwright + TypeScript | Completed / Portfolio Ready

Playwright-ParaBank-Automation – Automation Strategy

Document Information

ItemValue
Version1.0.0
StatusCompleted / Portfolio Ready
Primary browserGoogle Chrome
Execution modelPlaywright Test

Strategy

The automation strategy is based on the existing manual QA scenarios. Each mapped TC001–TC070 case is implemented as a Playwright test where the application and environment permit reliable automation.

Test Design Coverage

Test Organization

Tests are grouped by business module. Data-driven framework demonstrations are intentionally separated into tests/data-driven/ and do not replace the original TC001–TC070 mapping.

Locator Strategy

The framework prefers semantic and stable locators such as role, label, name and stable application attributes. CSS selectors are used where ParaBank does not expose a suitable semantic locator.

Known ParaBank instability is documented rather than hidden. For TC033, TC034, TC036, TC037 and TC053, application behavior/locator limitations were established during execution and investigation; the tests preserve the best available evidence for the environment.

Waiting Strategy

The framework relies primarily on Playwright's auto-waiting and explicit assertions. A shared 3-second stabilization wait is retained because the local ParaBank instance demonstrated timing instability during development. This is an environment-specific mitigation, not a general recommendation to use arbitrary sleeps.

Test Isolation

Tests create unique registration users through RegistrationDataFactory where registration is part of the flow. Shared browser cookies are cleared by the base fixture before each test.

Execution

Default configuration uses one worker to reduce interference against the unstable local demo application. A command-line --workers=N override can be used for controlled parallel experiments or CI environments.

Evidence

The configuration uses:

screenshot: only-on-failure
video: retain-on-failure
trace: on-first-retry

This provides actionable evidence without storing unnecessary artifacts for every successful test.

Reporting

The framework uses three reporters:

  1. list for immediate terminal feedback.
  2. html for Playwright's interactive report.
  3. allure-playwright for the portfolio-oriented Allure report.

Defect Philosophy

A failing automation test is not automatically treated as an automation defect. Where the application accepts invalid data, exposes misleading validation, or behaves inconsistently, the test records the observed behavior and supporting evidence. Assertions are not weakened solely to make the suite green.

Completion Statement

The automation strategy for the completed project baseline is established and implemented.